Vehicle computing systems and methods for delivery of a mobile device lockout icon

ABSTRACT

A vehicle computing system includes at least one processor configured to provide a lockout icon to a mobile device using a uniform resource identifier. The at least one processor is further configured to, in response to established communication with the mobile device having a user-interface display, retrieve the uniform resource identifier based on an application being executed at the mobile device. The at least one processor is further configured to transmit the uniform resource identifier to the mobile device to lockout the user-interface display with the lockout icon associated with the uniform resource identifier.

TECHNICAL FIELD

The present disclosure relates generally to icons, and more particularlyto a vehicle computing system configured to provide a lockout icon to amobile device.

BACKGROUND

Vehicle based computing systems are growing in popularity. Using varioussources of vehicle information as well as driver inputs and connectionsto vehicle systems, the computing system may add a variety offunctionality and novelty to the driving experience. Furthermore,systems may often communicate with remote devices either to gaininformation from those devices, or to use those devices to access anapplication. For example, the vehicle computing system may communicatewith a mobile device, and use the mobile device's ability to execute anapplication at the mobile device to send and receive information fromthe application. With the integration of a variety of functionalitybeing received from the mobile device, the driving experience may beimproved by directing driver input to a vehicle user interface for thevehicle-based computing system instead of to the mobile deviceinterface.

SUMMARY

In at least one embodiment, a vehicle computing system includes at leastone processor configured to provide a lockout icon to a mobile deviceusing a uniform resource identifier. The at least one processor isfurther configured to, in response to established communication with themobile device having a user interface display, retrieve the uniformresource identifier based on an application being executed at the mobiledevice. The at least one processor is further configured to transmit theuniform resource identifier to the mobile device to lock out the userinterface display with the lockout icon associated with the uniformresource identifier.

In at least one embodiment, a mobile device includes a display and aprocessor configured to communicate with a vehicle computing system. Theprocessor is further configured to transmit a message to notify thevehicle computing system of an application in a foreground state. Theprocessor is further configured to receive a uniform resource locatorfrom the VCS. The processor is further configured to transmit theuniform resource locator to a server. The processor is furtherconfigured to output the lockout icon at the display based on a receivedlockout icon from the server associated with the uniform resourcelocator.

In at least one embodiment, a computer-program product embodied in anon-transitory computer readable medium that is programmed for a vehicleprocessor and comprising instructions for storing a uniform resourcelocator associated with an image. The computer-program product includesfurther instructions for establishing a communication connection with amobile device. The computer-program product includes furtherinstructions for transmitting the uniform resource locator based on anapplication being executed in a foreground state at the mobile device,wherein the uniform resource locator provides the image at a display ofthe mobile device for locking-out user interaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a representative block topology of a vehicle infotainmentsystem implementing a user-interactive vehicle information displaysystem according to an embodiment;

FIG. 2 is a representative block topology of a system for integratingone or more connected devices with the vehicle based computing systemaccording to an embodiment;

FIG. 3 is a block diagram illustrating the vehicle based computingsystem in communication with a connected device according to anembodiment;

FIG. 4 is a flow chart illustrative of the vehicle based computingsystem providing a lockout image to the connected device using a uniformresource locator according to an embodiment; and

FIG. 5 is a flow chart illustrative of the mobile device outputting alockout icon based on a connection with the vehicle based computingsystem according to an embodiment.

DETAILED DESCRIPTION

Embodiments of the present disclosure are described herein. It is to beunderstood, however, that the disclosed embodiments are merely examplesand other embodiments can take various and alternative forms. Thefigures are not necessarily to scale; some features could be exaggeratedor minimized to show details of particular components. Therefore,specific structural and functional details disclosed herein are not tobe interpreted as limiting, but merely as a representative basis forteaching one skilled in the art to variously employ the embodiments. Asthose of ordinary skill in the art will understand, various featuresillustrated and described with reference to any one of the figures canbe combined with features illustrated in one or more other figures toproduce embodiments that are not explicitly illustrated or described.The combinations of features illustrated provide representativeembodiments for typical applications. Various combinations andmodifications of the features consistent with the teachings of thisdisclosure, however, could be desired for particular applications orimplementations.

The embodiments of the present disclosure generally provide for aplurality of circuits or other electrical devices. All references to thecircuits and other electrical devices and the functionality provided byeach, are not intended to be limited to encompassing only what isillustrated and described herein. While particular labels may beassigned to the various circuits or other electrical devices disclosed,such labels are not intended to limit the scope of operation for thecircuits and the other electrical devices. Such circuits and otherelectrical devices may be combined with each other and/or separated inany manner based on the particular type of electrical implementationthat is desired. It is recognized that any circuit or other electricaldevice disclosed herein may include any number of microprocessors,integrated circuits, memory devices (FLASH, random access memory (RAM),read only memory (ROM), electrically programmable read only memory(EPROM), electrically erasable programmable read only memory (EEPROM),or other suitable variants thereof, for example) and software whichco-act with one another to perform operation(s) disclosed herein. Inaddition, any one or more of the electric devices may be configured toexecute a computer program that is embodied in a non-transitory computerreadable medium that is programmed to perform any number of thefunctions as disclosed.

The disclosure relates to a locked screen icon that is displayed on amobile device user interface when the mobile device is connected to avehicle computing system. The vehicle computing system may store auniform resource locater that is associated with a predefined iconstored at a remote server. The vehicle computing system may establish acommunication link with the mobile device. The vehicle computing systemmay receive a notification from an application being executed at themobile device. In response to the notification, the vehicle computingsystem may transmit the stored uniform resource locator to the mobiledevice so that a specific icon image may be displayed at the mobiledevice user interface as a locked screen for the mobile device. Thepurpose of the locked screen icon is to encourage a user to control theapplication being executed at the mobile device from a vehicle interfaceor head unit, rather than controlling the application directly from themobile device.

The locked screen icon may be updated and stored at a remote server. Thelocked screen icon may be configured as a generic or branded icon for anapplication stored at the mobile device. The vehicle computing systemmay be configured by the vehicle manufacturer to update the icon througha server or vehicle computing system without requesting the applicationdeveloper to update a logo image library in the application. Forexample, one or more vehicle manufacturers may implement the applicationexecuted at a mobile device while allowing the vehicle computing systemto output the locked screen icon with the respective vehicle manufacturebrand.

FIG. 1 illustrates an example block topology for a vehicle basedcomputing system 1 (VCS) for a vehicle 31. An example of such a VCS 1 isthe SYNC system manufactured by THE FORD MOTOR COMPANY. A vehicleenabled with a VCS 1 may contain a visual front end interface 4 locatedin the vehicle 31. The user may also be able to interact with theinterface if it is provided, for example, with a touch sensitive screen.In another illustrative embodiment, the interaction occurs throughbutton presses and/or spoken dialog with automatic speech recognitionand speech synthesis.

In the illustrative embodiment 1 shown in FIG. 1, a processor 3 controlsat least some portion of the operation of the vehicle-based computingsystem. Provided within the vehicle 31, the processor 3 allows onboardprocessing of commands and routines. Further, the processor 3 isconnected to both non-persistent 5 and persistent storage 7. In thisillustrative embodiment, the non-persistent storage 5 is random accessmemory (RAM) and the persistent storage 7 is a hard disk drive (HDD) orflash memory. In general, persistent (non-transitory) memory can includeall forms of memory that maintain data when a computer or other deviceis powered down. These include, but are not limited to, HDDs, CDs, DVDs,magnetic tapes, solid state drives, portable USB drives and any othersuitable form of persistent memory.

The processor 3 is also provided with a number of different inputsallowing the user to interface with the processor. In this illustrativeembodiment, a microphone 29, an auxiliary input 25 (for input 33), a USBinput 23, a GPS input 24, screen 4, which may be a touchscreen display,and a BLUETOOTH input 15 are all provided. An input selector 51 is alsoprovided, to allow a user to choose between various inputs. Input toboth the microphone and the auxiliary connector is converted from analogto digital by a converter 27 before being passed to the processor.Although not shown, numerous vehicle components and auxiliary componentsin communication with the VCS 1 may use a vehicle network (such as, butnot limited to, a CAN bus) to pass data to and from the VCS (orcomponents thereof).

For example, a near field communication (NFC) transceiver may beintegrated with the VCS 1. The NFC transceiver may communicate with theprocessor 3. The NFC transceiver 75, such as a Texas Instrument™TRF7970A, may be configured to communicate with one or more mobiledevices. The NFC transceiver may include an RFID tag, a loop antenna, aflexible fabric packaging material and an EMI shielding material. TheNFC transceiver may be used to communicate and authentic a mobiledevice. For example, the NFC transceiver may communicate with the mobiledevice configured with NFC and having an application embedded within themobile device computing system.

Outputs to the system can include, but are not limited to, a visualdisplay 4 and a speaker 13 or stereo system output. The speaker 13 isconnected to an amplifier 11 and receives its signal from the processor3 through a digital-to-analog converter 9. Output can also be made to aremote BLUETOOTH device such as PND 54 or a USB device such as vehiclenavigation device 60 along the bi-directional data streams shown at 19and 21, respectively.

In one illustrative embodiment, the system 1 uses the BLUETOOTHtransceiver 15 to communicate 17 with a user's mobile device 53 (cellphone, smart phone, tablet, PDA, or any other device having wirelessremote network connectivity, for example). The mobile device (nomadicdevice, for example) can then be used to communicate 59 with a network61 outside the vehicle 31 through, for example, communication 55 with acellular tower 57. In some embodiments, tower 57 may be a WiFi accesspoint. Communication between the mobile device 53 and the BLUETOOTHtransceiver is generally represented by signal 14.

Pairing a mobile device 53 and the BLUETOOTH transceiver 15 can beinstructed through a button 52 or similar input. Accordingly, the CPU 3is instructed that the onboard BLUETOOTH transceiver will be paired witha BLUETOOTH transceiver in a mobile device 53.

Data may be communicated between CPU 3 and network 61 utilizing, forexample, a data-plan, data over voice, or DTMF tones associated withnomadic device 53. Alternatively, it may be desirable to include anonboard modem 63 having antenna 18 in order to communicate 16 databetween CPU 3 and network 61 over the voice band. The nomadic device 53can then be used to communicate 59 with a network 61 outside the vehicle31 through, for example, communication 55 with a cellular tower 57. Insome embodiments, the modem 63 may establish communication 20 with thetower 57 for communicating with network 61. As a non-limiting example,modem 63 may be a USB cellular modem and communication 20 may becellular communication.

In one illustrative embodiment, the processor 3 is provided with anoperating system including an application program interface (API) tocommunicate with modem application software. An example of such an APIis the SmartDeviceLink project providing a software framework tointegrate brought in applications onto the VCS. The modem applicationsoftware may access an embedded module or firmware on the BLUETOOTHtransceiver to complete wireless communication with a remote BLUETOOTHtransceiver (such as that found in a mobile device). Bluetooth is asubset of the IEEE 802 PAN (personal area network) protocols. IEEE 802LAN (local area network) protocols include WiFi and have considerablecross-functionality with IEEE 802 PAN. Both are suitable for wirelesscommunication within a vehicle. Another communication means that can beused in this realm is free-space optical communication (such as IrDA)and non-standardized consumer IR protocols.

In another embodiment, mobile device 53 includes a modem for voice bandor broadband data communication. In the data-over-voice embodiment, atechnique known as frequency division multiplexing may be implementedwhen the owner of the mobile device can talk over the device while datais being transferred. At other times, when the owner is not using thedevice, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHzin one example). While frequency division multiplexing may be common foranalog cellular communication between the vehicle and the internet, andis still used, it has been largely replaced by hybrids of Code DomainMultiple Access (CDMA), Time Domain Multiple Access (TDMA), andSpace-Domain Multiple Access (SDMA) for digital cellular communication.These are all ITU IMT-2000 (3G) compliant standards and offer data ratesup to 2 mbs for stationary or walking users and 385 kbs for users in amoving vehicle. 3G standards are now being replaced by IMT-Advanced (4G)which offers 100 mbs for users in a vehicle and 1 gbs for stationaryusers. If the user has a data-plan associated with the nomadic device,it is possible that the data plan allows for broad-band transmission andthe system could use a much wider bandwidth (speeding up data transfer).In still another embodiment, mobile device 53 is replaced with acellular communication device that is installed to vehicle 31. In yetanother embodiment, the mobile device (the nomadic device illustrated asND 53, for example) may be a wireless local area network (LAN) devicecapable of communication over, for example (and without limitation), an802.11g network (i.e., WiFi) or a WiMax network.

In one embodiment, incoming data can be passed through the mobile device53 via a data-over-voice or data-plan, through the onboard BLUETOOTHtransceiver and into the vehicle's internal processor 3. In the case ofcertain temporary data, for example, the data can be stored on the HDDor other storage media 7 until such time as the data is no longerneeded.

Additional sources that may interface with the vehicle include apersonal navigation device 54, having, for example, a USB connection 56and/or an antenna 58, a vehicle navigation device 60 having a USB 62 orother connection, an onboard GPS device 24, or remote navigation system(not shown) having connectivity to network 61. USB is one of a class ofserial networking protocols. IEEE 1394 (FireWire™ (Apple), i.LINK™(Sony), and Lynx™ (Texas Instruments)), EIA (Electronics IndustryAssociation) serial protocols, IEEE 1284 (Centronics Port), S/PDIF(Sony/Philips Digital Interconnect Format) and USB-IF (USB ImplementersForum) form the backbone of the device-device serial standards. Most ofthe protocols can be implemented for either electrical or opticalcommunication.

Further, the CPU could be in communication with a variety of otherauxiliary devices 65. These devices can be connected through a wireless67 or wired 69 connection. Auxiliary device 65 may include, but are notlimited to, personal media players, wireless health devices, portablecomputers, and the like.

Also, or alternatively, the CPU could be connected to a vehicle basedwireless router 73, using for example a WiFi (IEEE 803.11) 71transceiver. This could allow the CPU to connect to remote networks inrange of the local router 73.

In addition to having various processes executed by a vehicle computingsystem located in a vehicle, in certain embodiments, processes may beexecuted by a computing system in communication with a vehicle computingsystem. Such a system may include, but is not limited to, a wirelessmobile device (mobile phone, for example) or a remote computing system(a server, for example) connected through the wireless device.Collectively, such systems may be referred to as vehicle associatedcomputing systems (VACS). In certain embodiments, particular componentsof the VACS may perform particular portions of a process depending onthe particular implementation of the system. By way of example and notlimitation, if a process includes sending or receiving information witha paired wireless device, then it is likely that the wireless device isnot performing the process, since the wireless device would not “sendand receive” information with itself. One of ordinary skill in the artwill understand when it is inappropriate to apply a particular VACS to agiven solution. In all solutions, it is contemplated that at least thevehicle computing system (VCS) located within the vehicle itself iscapable of performing the representative processes.

FIG. 2 is a representative block topology of a system 100 forintegrating one or more connected devices with the VCS 1. The CPU 3 maybe in communication with one or more transceivers. The one or moretransceivers are capable for wired and wireless communication for theintegration of one or more devices. To facilitate the integration, theCPU 3 may include a device integration framework 101 configured toprovide various services to the connected devices. These services mayinclude transport routing of messages between the connected devices andthe CPU 3, global notification services to allow connected devices toprovide alerts to the user, application launch and management facilitiesto allow for unified access to applications executed by the CPU 3 andthose executed by the connected devices, provide a user interfacelockout icon to prevent a user from interacting with the mobile device,and point of interest location and management services for variouspossible vehicle destinations. For example, the CPU 3 may output one ormore applications at the display 4 that are executed at the connectedmobile device 53.

In another example, the CPU 3 may transmit an icon lockout screenrequest to the mobile device 53. The icon lockout screen request mayinclude a uniform resource locator so that the mobile device 53 mayretrieve a specific icon associated with the CPU 3. In response to theicon lockout screen request, the mobile device 53 may communicate with aremote server to receive the icon stored at the uniform resourcelocator. The mobile device 53 may lock out a user interface screen whiledisplaying the icon. The displayed icon lockout user interface screenmay prevent a user from interacting with a mobile device user interfacewhile the mobile device 53 is communicating with the VCS 1.

As mentioned above, the CPU 3 of the VCS 1 may be configured tointerface with one or more mobile devices 53 of various types. Themobile device 53 may further include a device integration clientcomponent 103 to allow the mobile device 53 to take advantage of theservices provided by the device integration framework 101. Theintegration client component 103 may include an application programinterface to enable the interaction between the mobile device 53 and theVCS 1. The mobile device 53 may execute one or more applicationsincluding, but not limited to, 911 Assist™ 105, internet radio 107,navigation 109, OpenTable™ 111, etc. The one or more applications may bein a background state 110, a closed state 112 or a foreground state 114at the mobile device 53. The CPU 3 may output the one or moreapplications at the display 4. For example, in response to anestablished communication with the mobile device 53, the CPU 3 mayindicate whether the one or more applications are in the foregroundstate, background state or closed state. In one example, the VCS maydisplay the one or more applications in a foreground state, backgroundstate, or closed state based on the color, brightness and/or shading ofan icon representing the application(s).

In one example, the VCS 1 may receive a message that an application hasentered a foreground state at the mobile device 53. The VCS 1 maytransmit the uniform resource locater to the mobile device based on theapplication entering the foreground state. The mobile device 53 mayretrieve an icon display based on the uniform resource locator via aninternet connection. The mobile device 53 may lock out the mobile deviceuser interface by outputting the icon retrieved at the uniform resourcelocator.

The mobile device 53 may transmit application notifications to the CPU 3so that the VCS 1 may track which application is in the foregroundstate. For example, the VCS 1 may receive a message that the internetradio application 107 is running in the foreground state 114. The VCS 1may output an icon at the in-vehicle display 4 for the internet radioapplication 107 indicating that it is in the foreground state 114. TheVCS 1 may be configured to transmit an updated uniform resource locatorfor an icon based on a new application being executed in the foregroundstate.

In one example, the VCS 1 may receive an application launch request for911 Assist™ 105. The VCS 1 may receive a manually input 911 Assist™application 105 launch request via the display 4 and/or an automaticallyinput request based on a received emergency notification via an advancedcrash safety module (ACSM). In response to the 911 Assist™ 105 in thebackground state 110 at the mobile device 53, the CPU 3 may transmit alaunch request for the 911 Assist™ application 105. For example, thelaunch request may include a unique application identifier for the 911Assist™ application 105. In response to receiving the launch message forthe 911 Assist™ application 105 at the mobile device 53, the mobiledevice may disable the lockout at the mobile device user interface sothat a user and/or emergency personnel may access the mobile device 53.

The one or more transceivers may include a multiport connector hub 102.The multiport connector hub 102 may be used to interface between the CPU3 and additional types of connected devices other than the mobile device53. The multiport connector hub 102 may communicate with the CPU 3 overvarious buses and protocols, such as via USB, and may furthercommunicate with the connected devices using various other connectionbuses and protocols, such as Serial Peripheral Interface Bus (SPI),Inter-integrated circuit (I2C), and/or Universal AsynchronousReceiver/Transmitter (UART). The multiport connector hub 102 may furtherperform communication protocol translation and interworking servicesbetween the protocols used by the connected devices and the protocolused between the multiport connector hub 102 and the CPU 3. Theconnected devices may include, as some non-limiting examples, a radardetector 104, a global position receiver device 106, and a storagedevice 108. The CPU 3 may receive a message from the connected devicesindicating applications running in the foreground state. The CPU 3 maytransmit a request to lock out user input functions at the connecteddevice. For example, in response to a connected device not having a userinterface display, the connected device may lock out functionality ofone or more hard input buttons based on the icon lockout screen requestreceived from the VCS 1. In another example, the connected device maylock out a connected device user interface screen based on the iconlockout screen request.

FIG. 3 is a block diagram illustrating the VCS 1 in communication with aconnected device 53 according to an embodiment. The VCS 1 may includeone or more processors (CPU 3, for example), a wireless transceiver, andan in-vehicle display 4. The mobile device 53 may include one or moreprocessors (CPU 201, for example), a wireless transceiver, and a mobiledevice user interface display 203. The remote server 61 may include oneor more processors, a database, and/or a communication link within anantenna 19 to communicate data with the mobile device 53.

The VCS 1 may establish communication with the mobile device 53 via ahandshake process 202. The handshake process 202 may include a series ofcommunications back and forth between the VCS 1 and mobile device 53 forsystem access authentication. If the handshake is complete, the VCS 1may receive data from an application executed at the mobile device 53.For example, the handshake process may include the exchange ofinformation to detect whether or not the mobile device 53 has beenpaired with the VCS 1. In another example, the VCS 1 may be executing anapplication associated with the mobile device 53. The application mayhave a key configured to verify that the VCS 1 is authorized tocommunicate with the mobile device 53.

The VCS 1 may communicate application data 204 with the mobile device53. For example, the application data from the mobile device 53 mayinclude messages received from one or more applications registered tocommunicate with the VCS 1. In response to the application data, the VCS1 may retrieve a uniform resource locator (also known as a uniformresource identifier, URL, etc., for example) 206 based on a registeredapplication. The VCS 1 may transmit the uniform resource locator (URL)210 to the mobile device 53. The VCS 1 may output an application icon atthe in-vehicle display 208 based on the application data.

The mobile device 53 may search for an internet connection based on thereceived URL. The mobile device 53 may transmit a request for an iconvia the URL 212 at the remote server 61 based on the internetconnection. The mobile device 53 may receive the icon stored at the URL214 from the remote server 61. The mobile device 53 may cache the icon215 in memory electrically connected to the CPU 201. The mobile device53 may transmit a lockout request while displaying the icon at the userinterface display 216. In one example, the mobile device 53 may output ageneric icon at the user interface display 216 if there is no internetconnection with the remote server 61.

In another example, the mobile device 53 may receive a request to launchan application from a background state to the foreground state. Themobile device 53 may transmit a message notifying the VCS 1 that theapplication is in the foreground state 216. In response to theapplication in the foreground state at the mobile device 53, the VCS 1may output the related icon 208 at the in-vehicle display 4. The VCS 1may transmit a message (transmit an updated URL, for example) to themobile device 53 based on the latest application entering the foregroundstate. The mobile device may retrieve a new icon based on the latestapplication to enter the foreground state. In one example, the mobiledevice may receive an updated URL based on the latest application beinglaunched in the foreground state. The mobile device may retrieve theupdated icon via the updated URL at the remote server 61. The mobiledevice may transmit the updated icon and lockout screen 218 to themobile device user interface display 203.

The mobile device may be configured to have a predefined timerassociated with the cached icon. For example, in response to an amountof time exceeding the predefined timer, the mobile device may transmit arequest to update the cached icon using the URL 219. The mobile device53 may output the icon based on the update to the cached icon.

FIG. 4 is a flow chart illustrative of the vehicle based computingsystem providing a lockout image to the connected device using a uniformresource locator according to an embodiment. The method 300 may beimplemented using software code contained within the VCS 1. In otherembodiments, the method 300 may be implemented in other vehiclecontrollers, distributed among multiple vehicle controllers, or executedat a remote controller in communication with the VCS 1.

Referring again to FIG. 4, the vehicle and its components illustrated inFIG. 1, FIG. 2, and FIG. 3 are referenced throughout the discussion ofthe method 300 to facilitate understanding of various aspects of thepresent disclosure. The method 300 of providing a lockout icon to amobile device 53 may be implemented through a computer algorithm,machine executable code, or software instructions programmed into asuitable programmable logic device(s) of the vehicle, such as thevehicle control module, the device control module, another controller incommunication with the vehicle computing system, or a combinationthereof. Although the various operations shown in the flowchart diagram300 appear to occur in a chronological sequence, at least some of theoperations may occur in a different order, and some operations may beperformed concurrently or not at all.

In operation 302, the VCS 1 may be initialized and enabled based on akey-on position of an ignition system. The VCS 1 may initialize the oneor more applications for execution in operation 304. In response to theinitialization of the VCS 1, the system may display the one or moreapplications at a user interface in operation 306.

In operation 308, the VCS 1 may enable a wireless communicationtransceiver to search for a mobile device 53 requesting to connect withthe system. If the VCS 1 detects no mobile device 53 requesting toconnect, the system may continue to output a wireless communicationmessage via the transceiver.

If the mobile device 53 is detected, the VCS 1 may attempt to connectusing a wireless communication link via the transceiver in operation310. The communication link may include wireless communicationtechnology (Bluetooth, Bluetooth low energy, WiFi, etc., for example).In response to the communication link with the mobile device 53, the VCS1 may receive data from one or more application executed at the mobiledevice 53.

In operation 312, the VCS 1 may determine if the application executed atthe mobile device 53 is registered as a supported application. Forexample, the VCS 1 may compare an application identifier to a databaseof approved applications to determine if the application being executedat the mobile device 53 is registered to communicate with the system. Inresponse to a registered application, the VCS 1 may retrieve a storedURL in operation 314. The VCS 1 may transmit the URL to the mobiledevice 53 in operation 316. In response to the transmission of the URL,the VCS 1 may end the method 300 of the VCS 1 providing the lockout icon(image displayed at the mobile device user interface, for example) tothe mobile device 53 in operation 318.

FIG. 5 is a flow chart illustrative of the mobile device 53 outputting alockout icon based on a connection with the VCS 1 according to anembodiment. The method 400 may be implemented using software codecontained within the mobile device 53. In other embodiments, the method400 may be implemented in other processors in communication with themobile device 53, distributed among multiple processors including theVCS 1, or a combination thereof.

In operation 402, the mobile device 53 may be initialized and enabledbased on a power-on request. The mobile device 53 may initialize one ormore applications for execution based on the power-on request inoperation 404. In response to the initialization of the mobile device53, the device may output one or more applications at a user interfacein operation 406.

In operation 408, the mobile device 53 may enable a wirelesscommunication transceiver to search for the VCS 1 requesting to connectwith the device. If the mobile device 53 detects no VCS 1 requesting toconnect, the device may continue to output a wireless communicationmessage via the transceiver.

If the VCS 1 is detected, the mobile device 53 may attempt to connectusing a wireless communication link via the transceiver in operation410. In response to the communication link, the mobile device 53 mayreceive the icon lockout screen request in operation 412. The iconlockout screen request may include the icon URL.

In operation 414, the mobile device 53 may search for an internetconnectivity communication link. If there is no internet communicationlink, the mobile device 53 may retrieve a generic icon for output as thelockout screen display for the mobile device user interface in operation416. In response to an established internet communication link, themobile device 53 may retrieve the icon via the URL at the remote serverin operation 418. The mobile device may cache the icon received from theremote server in operation 420.

In operation 422, the mobile device 53 may determine if the applicationis in use, therefore being executed in the foreground state. In responseto the application in the foreground state, the mobile device 53 maylockout the mobile device user interface and output the retrieved iconvia the URL or the generic icon in operation 424. In response to theoutput of the icon lockout screen at the mobile device user interfacedisplay, the mobile device 53 may end the method 400 in operation 426.

The embodiments disclosed above enable application developers to createa mobile application that may be used on multiple vehicle telematicssystems. The disclosure presents embodiments of a vehicle telematicssystem that transmits an icon via the URL associated with the system tothe mobile device when communicating with the mobile application. Theicon provides a brand presence to a customer associated with the vehicleand infotainment system at the mobile device.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms encompassed by the claims.The words used in the specification are words of description rather thanlimitation, and it is understood that various changes can be madewithout departing from the spirit and scope of the disclosure. Aspreviously described, the features of various embodiments can becombined to form further embodiments of the invention that may not beexplicitly described or illustrated. While various embodiments couldhave been described as providing advantages or being preferred overother embodiments or prior art implementations with respect to one ormore desired characteristics, those of ordinary skill in the artrecognize that one or more features or characteristics can becompromised to achieve desired overall system attributes, which dependon the specific application and implementation. These attributes caninclude, but are not limited to cost, strength, durability, life cyclecost, marketability, appearance, packaging, size, serviceability,weight, manufacturability, ease of assembly, etc. As such, embodimentsdescribed as less desirable than other embodiments or prior artimplementations with respect to one or more characteristics are notoutside the scope of the disclosure and can be desirable for particularapplications.

What is claimed is:
 1. A vehicle computing system comprising: at leastone processor configured to, in response to establishing communicationwith a mobile device having a user interface display, retrieve a uniformresource identifier corresponding to an application being executed in aforeground state at the mobile device; and transmit the uniform resourceidentifier to the mobile device to lock out the user interface displaywith a lockout icon retrieved from the uniform resource identifier. 2.The vehicle computing system of claim 1, wherein the processor isfurther configured to receive a notification requesting the uniformresource identifier from the mobile device responsive to the applicationentering the foreground state.
 3. The vehicle computing system of claim1, wherein the processor is further configured to communicate with anin-vehicle display and output a vehicle icon associated with theapplication executed at the mobile device at the in-vehicle display. 4.The vehicle computing system of claim 1, wherein the mobile device isconfigured to, in response to establishing communication with a remoteserver, transmit the uniform resource identifier to the remote serverand receive the lockout icon associated with the uniform resourceidentifier from the remote server.
 5. The vehicle computing system ofclaim 4, wherein the lockout of the user interface display at the mobiledevice prevents a user from interacting with one or more functions atthe user interface display.
 6. The vehicle computing system of claim 4,wherein the remote server is configured to store the lockout iconassociated with the uniform resource identifier.
 7. A mobile devicecomprising: a display; and a processor configured to, in response to anestablishing communication with a vehicle computing system (VCS),transmit a message to notify the VCS of an application in a foregroundstate; receive a uniform resource locator (URL) from the VCS, the URLcorresponding to the application in the foreground state; transmit theURL to a server; and in response to a received lockout icon from theserver associated with the URL, output the lockout icon at the display.8. The mobile device of claim 7, wherein the processor is furtherconfigured to, in response to the output of the lockout icon, lock outat least one of the display and an input button to prevent a user frominteracting with the display and the input button.
 9. The mobile deviceof claim 7, wherein the processor is further configured to, detect aninternet connection to communicate with the server, and if no internetconnection is detected, output a generic lockout icon at the display.10. The mobile device of claim 7, wherein the processor is furtherconfigured to cache the lockout icon in memory electrically connected tothe processor, and to update the lockout icon in the memory based on apredefined timer.
 11. The mobile device of claim 7, wherein the serveris configured to store the lockout icon associated with the URL.
 12. Themobile device of claim 7, wherein the processor is further configuredto, in response to a disconnection request received from the VCS, removethe lockout icon from the display to allow user interaction with thedisplay.
 13. A computer-program product embodied in a non-transitorycomputer readable medium for a vehicle processor comprising instructionsfor: storing a plurality of uniform resource locators (URLs), eachcorresponding to an icon of a different application; and in response toan establishing connection with a mobile device, transmitting the URLcorresponding to the one of the applications being executed in aforeground state at the mobile device to cause the mobile device toretrieve the icon to display on a lockout screen.
 14. Thecomputer-program product of claim 13, the non-transitory computerreadable medium further comprising instructions for receiving aforeground state notification from the application requesting the URL.15. The computer-program product of claim 13, the non-transitorycomputer readable medium further comprising instructions forcommunicating with an in-vehicle display and outputting a vehicle iconassociated with the application executed at the mobile device to thein-vehicle display.
 16. The computer-program product of claim 13,wherein the mobile device is configured to, in response to establishingcommunication with a remote server, transmit the uniform resourcelocator to the remote server and receive the image associated with theURL from the remote server.
 17. The computer-program product of claim16, wherein the icon received from the remote server is cached in memoryat the mobile device.
 18. The computer-program product of claim 17,wherein the cached image is updated by a request via the URL to theremote server based on a predefined timer.
 19. The computer-programproduct of claim 16, wherein the remote server is configured to storethe icon associated with the URL.
 20. The computer-program product ofclaim 13, wherein the locking-out of the display at the mobile deviceprevents a user from interacting with one or more functions at thedisplay.